v7.114.0

Compare Source

Important Changes

• fix(browser/v7): Continuously record CLS (#​11935)

This release fixes a bug that caused the cumulative layout shift (CLS) web vital not to be reported in a majority of the
cases where it should have been reported. With this change, the CLS web vital should now always be reported for
pageloads with layout shift. If a pageload did not have layout shift, no CLS web vital should be reported.

Please note that upgrading the SDK to this version may cause data in your dashboards to drastically change.

Other Changes

• build(aws-lambda/v7): Turn off lambda layer publishing (#​11875)
• feat(v7): Add tunnel support to multiplexed transport (#​11851)
• fix(opentelemetry-node): support HTTP_REQUEST_METHOD attribute (#​11929)
• fix(react/v7): Fix react router v4/v5 span names (#​11940)

v7.113.0

Compare Source

Important Changes

• feat(node): Support Node 22 (#​11754)

This release adds support for Node 22! 🎉

It also adds prebuilt-binaries for Node 22 to @sentry/profiling-node.

Other Changes

• feat(feedback): [v7] New feedback button design (#​11841)
• feat(replay/v7): Upgrade rrweb packages to 2.15.0 (#​11752)
• fix(ember/v7): Ensure unnecessary spans are avoided (#​11848)

v7.112.2

Compare Source

• fix(nextjs|sveltekit): Ensure we can pass browserTracingIntegration (#​11765)

v7.112.1

Compare Source

• fix(ember/v7): Do not create rendering spans without transaction (#​11750)

v7.112.0

Compare Source

Important Changes

• feat: Export pluggable integrations from SDK packages (#​11723)

Instead of installing @sentry/integrations, you can now import the pluggable integrations directly from your SDK
package:

// Before
import * as Sentry fromv '@​sentry/browser';
import { dedupeIntegration } from '@​sentry/integrations';

Sentry.init({
  integrations: [dedupeIntegration()],
});

// After
import * as Sentry from '@​sentry/browser';

Sentry.init({
  integrations: [Sentry.dedupeIntegration()],
});

Note that only the functional integrations (e.g. xxxIntegration()) are re-exported.

Other Changes

• feat(replay): Add "maxCanvasSize" option for replay canvases (#​11732)
• fix(serverless): [v7] Check if cloud event callback is a function (#​11734)

Bundle size 📦

v7.111.0

Compare Source

• feat(core): Add server.address to browser http.client spans (#​11663)
• fix: Ensure next & sveltekit correctly handle browserTracingIntegration (#​11647)
• fix(browser): Don't assume window.document is available (#​11598)

Bundle size 📦

v7.110.1

Compare Source

• fix(nextjs): Fix tunnelRoute matching logic for hybrid cloud (#​11577)

Bundle size 📦

v7.110.0

Compare Source

Important Changes

• feat(tracing): Add interactions sample rate to browser tracing integrations (#​11382)

You can now use a interactionsSampleRate to control the sample rate of INP spans. interactionsSampleRate is applied
on top of the global tracesSampleRate. Therefore if interactionsSampleRate is 0.5 and tracesSampleRate is 0.1,
then the actual sample rate for interactions is 0.05.

Sentry.init({
  tracesSampleRate: 0.1,
  integrations: [
    Sentry.browserTracingIntegration({
      interactionsSampleRate: 0.5,
    }),
  ],
});

• Deprecations

This release deprecates the Hub class, as well as the addRequestDataToTransaction method. The trpcMiddleware
method is no longer on the Handlers export, but instead is a standalone export.

Please see the detailed Migration docs on how to migrate to the new APIs.

• feat: Deprecate and relocate trpcMiddleware (#​11389)
• feat(core): Deprecate Hub class (#​11528)
• feat(types): Deprecate Hub interface (#​11530)
• ref: Deprecate addRequestDataToTransaction (#​11368)

Other Changes

• feat(core): Update metric normalization (#​11519)
• feat(feedback): Customize feedback placeholder text color (#​11521)
• feat(remix): Skip span creation for OPTIONS and HEAD request. (#​11485)
• feat(utils): Add metric buckets rate limit (#​11506)
• fix(core): unref timer to not block node exit (#​11483)
• fix(metrics): Map statsd to metric_bucket (#​11505)
• fix(spans): Allow zero exclusive time for INP spans (#​11408)
• ref(feedback): Configure feedback fonts (#​11520)

Bundle size 📦

v7.109.0

Compare Source

This release deprecates some exports from the @sentry/replay package. These exports have been moved to the browser SDK
(or related framework SDKs like @sentry/react).

• feat(feedback): Make "required" text for input elements configurable (#​11287)
• feat(node): Add scope to ANR events (#​11267)
• feat(replay): Bump rrweb to 2.12.0 (#​11317)
• fix(node): Local variables skipped after Promise (#​11248)
• fix(node): Skip capturing Hapi Boom error responses (#​11324)
• fix(web-vitals): Check for undefined navigation entry (#​11312)
• ref(replay): Deprecate @sentry/replay exports (#​11242)

Work in this release contributed by @​soerface. Thank you for your contribution!

Bundle size 📦

v7.108.0

Compare Source

This release fixes issues with Time to First Byte (TTFB) calculation in the SDK that was introduced with 7.95.0. It
also fixes some bugs with Interaction to First Paint (INP) instrumentation. This may impact your Sentry Performance
Score calculation.

• feat(serverless): Add Node.js 20 to compatible runtimes (#​11104)
• feat(core): Backport ResizeObserver and googletag default filters (#​11210)
• feat(webvitals): Adds event entry names for INP handler. Also guard against empty metric value
• fix(metrics): use correct statsd data category (#​11187)
• fix(node): Record local variables with falsy values (v7) (#​11190)
• fix(node): Use unique variable for ANR context transfer (v7) (#​11162)
• fix(node): Time zone handling for cron (#​11225)
• fix(tracing): use web-vitals ttfb calculation (#​11231)
• fix(types): Fix incorrect sampled type on Transaction (#​11146)
• fix(webvitals): Fix mapping not being maintained properly and sometimes not sending INP spans (#​11183)

Work in this release contributed by @​quisido and @​joshkel. Thank you for your contributions!

Bundle size 📦

v7.107.0

Compare Source

This release fixes issues with INP instrumentation with the Next.js SDK and adds support for the enableInp option in
the deprecated BrowserTracing integration for backwards compatibility.

• feat(performance): Port INP span instrumentation to old browser tracing (#​11085)
• fix(ember): Ensure browser tracing is correctly lazy loaded (#​11027)
• fix(node): Do not assert in vendored proxy code (v7 backport) (#​11009)
• fix(react): Set handled value in ErrorBoundary depending on fallback [v7] (#​11037)

Bundle size 📦

v7.106.1

Compare Source

• fix(nextjs/v7): Use passthrough createReduxEnhancer on server (#​11010)

Bundle size 📦

v7.106.0

Compare Source

• feat(nextjs): Support Hybrid Cloud DSNs with tunnelRoute option (#​10958)
• feat(remix): Add Vite dev-mode support to Express instrumentation (#​10811)
• fix(core): Undeprecate setTransactionName
• fix(browser): Don't use chrome variable name (#​10874)
• fix(nextjs): Client code should not use Node global (#​10925)
• fix(node): support undici headers as strings or arrays (#​10938)
• fix(types): Add AttachmentType and use for envelope attachment_type property (#​10946)
• ref(ember): Avoid namespace import to hopefully resolve minification issue (#​10885)
• chore(sveltekit): Fix punctuation in a console.log (#​10895)

Work in this release contributed by @​jessezhang91 and @​bfontaine. Thank you for your contributions!

Bundle size 📦

v7.105.0

Compare Source

Important Changes

• feat: Ensure withActiveSpan is exported everywhere (#​10877)

You can use the withActiveSpan method to ensure a certain span is the active span in a given callback. This can be
used to create a span as a child of a specific span with the startSpan API methods:

const parentSpan = Sentry.startInactiveSpan({ name: 'parent' });
if (parentSpan) {
  withActiveSpan(parentSpan, () => {
    // This will be a direct child of parentSpan
    const childSpan = Sentry.startInactiveSpan({ name: 'child' });
  });
}

Bundle size 📦

v7.104.0

Compare Source

Important Changes

• feat(performance): create Interaction standalone spans on inp events (#​10709)

This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support
is released with the upcoming 24.3.0 release of self-hosted.

To opt-in to this feature, you can use the enableInp option in the browserTracingIntegration:

Sentry.init({
  integrations: [
    Sentry.browserTracingIntegration({
      enableInp: true,
    });
  ]
})

Other Changes

• feat(feedback): Flush replays when feedback form opens (#​10567)
• feat(profiling-node): Expose nodeProfilingIntegration (#​10864)
• fix(profiling-node): Fix dependencies to point to current versions (#​10861)
• fix(replay): Add errorHandler for replayCanvas integration (#​10796)

Bundle size 📦

v7.103.0

Compare Source

Important Changes

• feat(core): Allow to pass forceTransaction to startSpan() APIs (#​10819)

You can now pass forceTransaction: true to startSpan(), startSpanManual() and startInactiveSpan(). This allows
you to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to
the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if
possible, ensuring it shows up as a transaction throughout the system.

Please note that setting this to true does not guarantee that this will be sent as a transaction, but that the SDK
will try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it
in the Sentry UI.

Other Changes

• fix: Make breadcrumbs option optional in WinterCGFetch integration (#​10792)

Bundle size 📦